---
layout: default
title: YFII Improvement Proposals
---

<h1 class="page-heading">
  YFII Improvement Proposals
  <a href="https://discordapp.com/channels/736928317684580402/" rel="nofollow"
    ><img
      src="https://img.shields.io/discord/736928317684580402.svg?color=768AD4&label=discord&logo=https%3A%2F%2Fdiscordapp.com%2Fassets%2F8c9701b98ad4372b58f13fd9f65f966e.svg"
      alt="Discord"
      data-canonical-src="https://img.shields.io/discord/736928317684580402.svg?color=768AD4&amp;label=discord&amp;logo=https%3A%2F%2Fdiscordapp.com%2Fassets%2F8c9701b98ad4372b58f13fd9f65f966e.svg"
      style="max-width:100%;"
  /></a>
</h1>
<p>
  YFII Improvement Proposals (YIPs) describe standards for the YFII
  platform, including core protocol specifications, client APIs, and contract
  standards.
</p>

<h2>Contributing</h2>
<ol>
  <li>Review <a href="YIPS/yip-0">YIP-0</a>.</li>
  <li>Fork the repository by clicking "Fork" in the top right.</li>
  <li>
    Add your YIP to your fork of the repository. There is a
    <a href="https://github.com/yfii/YIPS/blob/master/yip-X.md"
      >template YIP here</a
    >.
  </li>
  <li>
    Submit a Pull Request to YFII's
    <a href="https://github.com/yfii/YIPS">YIPs repository</a>.
  </li>
</ol>

<p>
  Your first PR should be a first draft of the final YIP. It must meet the
  formatting criteria enforced by the build (largely, correct metadata in the
  header). An editor will manually review the first PR for a new YIP and assign
  it a number before merging it. Make sure you include a
  <code>discussions-to</code> header with the URL to a discussion forum or open
  GitHub issue where people can discuss the YIP as a whole.
</p>
<p>
  If your YIP requires images, the image files should be included in a
  subdirectory of the `assets` folder for that YIP as follow:
  <code>assets/yip-X</code> (for yip <b>X</b>). When linking to an image in the
  YIP, use relative links such as <code>../assets/yip-X/image.png</code>.
</p>
<p>
  When you believe your YIP is mature and ready to progress past the WIP phase,
  you should ask to have your issue added to the next governance call where it
  can be discussed for inclusion in a future platform upgrade. If the community
  agrees to include it, the YIP editors will update the state of your YIP to
  <code>Approved</code>.
</p>

<h2>YIP status terms</h2>
<ul>
  <li><strong>WIP</strong> - a YIP that is still being developed.</li>
  <li>
    <strong>Proposed</strong> - a YIP that is ready to be reviewed in a
    governance call.
  </li>
  <li>
    <strong>Approved</strong> - a YIP that has been accepted for implementation
    by the YFII community.
  </li>
  <li>
    <strong>Implemented</strong> - a YIP that has been released to mainnet.
  </li>
  <li><strong>Rejected</strong> - a YIP that has been rejected.</li>
</ul>
